Database Storage
All current and historical data is recorded and stored within the database utilized by CenterScape. The storage requirements of the database vary greatly depending on the number of attributes that require historical records and the frequency for which the data changes. CenterScape does not store the value of periodic readings, but rather stores updates to the previous value. Because of this and the nature of the data, temperature sensors, differential pressure sensors and power sensors tend to generate far more data than asset tracking tags. Additionally, calculated fields that have history enabled also drive large amounts of change when targeted at attributes that change often. For example, an average of four temperatures will require as much storage the individual readings of the four sensors. Historical information may be manually purged by month starting from the oldest month up to the previous month from the current month. Each point requires between 60b and 75b of storage.
Note: No consideration in storage size is made for transaction logging and these numbers are based on Postgres Server data file size and SQL Server running in Simple Recovery Mode. Transaction logs can grow to be multiples of the size of the actual data files and must be managed properly by truncating after full backups. If point in time restore is not required it is recommended that simple recovery mode be used.
Considerations For Sampling RF Code Sensors in Default Configuration
The following products have typical behaviors in any environment.
| Product | Typical Hourly Delta | Monthly Data Generated | Yearly Data Generated | 5 Year Storage |
|---|---|---|---|---|
| Temperature/Humidity Sensor | 42 Points/3.1KB | 2.2MB | 27MB | 130MB |
| Differential Pressure | 170 Points/12.5KB | 9.2MB | 110MB | 550MB |
| RPDU Tag | 220/16KB Points | 11.5MB | 138MB | 700MB |
Storage Considerations for “Edge” Condition Sensors in Default Configuration
The following products generate very little activity in most cases, but have edge conditions that may generate more activity.
| Product | Event Type | Single Event Storage | Per 100 Occurrences | Per 1000 Occurrences |
|---|---|---|---|---|
| Door Sensor | Each Time a Door Opens or Closes | 1 point/.07KB | 7KB | 70KB |
| Dry Contact | Each time a dry contact sensor is closed or opened. | 2 Points/ .15KB | 15KB | 150KB |
| Asset Tag Movement | Any time and asset moved from one detected location to another | 2-10 Points/ .15KB-1.5KB Depending on configuration. | 15KB to 150KB | 150KB-1.5MB |
| Online Status | Any time an asset or sensor tag times out and goes offline or is first seen by a reader. | 1 point/0.7KB | 70KB | 700KB |
To simplify the storage calculations, an Excel worksheet is available that will estimate the storage needs of CenterScape. https://rfcode.zendesk.com/hc/en-us/articles/360043318711-CenterScape-Storage-Calculator